Stop external-builder envelope 404 after block publication - #9948
Conversation
…(Gloas builder API 3/5) Third PR of the Gloas builder API stack: - beacon_chain: direct builder bid verification (spawned on the blocking executor), gossip-bid refinements, wei-domain bid selection (`BidCandidate`/`BidSource`), and Gloas block production that assembles local, gossip, and direct-builder candidates - network: process payload-bid and proposer-preference gossip, including the new `PayloadBidError` variants - client: construct the `Builders` service when the Gloas fork is scheduled and wire it into the beacon chain The HTTP API still serves `GET` produceBlockV4 at this point; the `POST` conversion and the `Eth-Builder-Url` round-trip land in the next PR. Change-Id: Ieccaee5db81bf871c19cef1b79fc48283be9dd51
…builder API 4/5) Fourth PR of the Gloas builder API stack (beacon-APIs sigp#630): - convert `/eth/v4/validator/blocks/{slot}` to POST with an optional `BuilderConfig` body (min_bid, builder_boost_factor, direct builders) - add `POST /eth/v1/validator/builder_preferences` for forwarding signed builder preferences - set `Eth-Builder-Url` on produceBlockV4 responses when a direct-builder bid wins, accept it on `POST /eth/v2/beacon/blocks`, and forward the signed block to that builder The validator client still uses the legacy GET methods at this point; it migrates in the final PR of this stack. Change-Id: I0ad30b8f36ad9b588ea1a0398220f92c9597bb95
…API 5/5) Final PR of the Gloas builder API stack: - sign builder request-auth and preferences (REQUEST_AUTH signing domain, web3signer message type) - add the builder configuration store (`builder_definitions.yml`) and book documentation - add the builder-preferences service and switch block production to `POST` produceBlockV4 with a `BuilderConfig` body, threading the `Eth-Builder-Url` header through block publication - remove the now-unused legacy `GET` produceBlockV4 client methods Change-Id: Iaeeaf6205a024e4fb9fd11aae6ac6a75978a8320
Changes: Skip validator payload-envelope handling after external-builder block publication. Cover self-build and external-builder envelope behaviour.
44f4424 to
17bcbc2
Compare
|
This pull request has merge conflicts. Could you please resolve them @jimmygchen? 🙏 |
17bcbc2 to
7c1ffce
Compare
| publish_envelope = | ||
| signed_execution_payload_bid.message.builder_index == BUILDER_INDEX_SELF_BUILD; |
There was a problem hiding this comment.
this reads the bid from this VC's own produce response, before sign_and_publish_block swaps in the block the cluster agreed on. for a DVT store those differ: one validator key is split into shares across N independent VC+BN pairs (SSV operators), sign_block runs consensus across them and usually returns another VC's block, and a threshold have to sign for anything to publish. so when this VC's own bid is external while the agreed block is self-build, the envelope step is skipped here and this VC's share goes missing. the reverse runs it with nothing to reveal.
sign_and_publish_block already holds the signed_block and drops it. suggest returning it (or just its bid) and deriving publish_envelope from that after the call. no-op for a normal store, where the block that comes back is the one that went in.
one thing to leave as-is: the fetch root. keep payload_envelope_block_root as unsigned_block.block_root(), just unconditionally. on the VC that built the agreed block the two roots are equal; on the others the agreed root is not in their own BN's pending_payload_envelopes (local building only, validator/execution_payload_envelopes.rs 404s otherwise), so keying on it would 404 everywhere and the store would never be called. they still need to sign, and anchor discards the fetched envelope on them anyway, so the fetch only has to succeed.
going to think deeper if i can handle this on anchor side, so commenting out the above for now
7c1ffce to
58eedb5
Compare
2c3656e to
39cf3c2
Compare
…(Gloas builder API 3/5) Third PR of the Gloas builder API stack: - beacon_chain: direct builder bid verification (spawned on the blocking executor), gossip-bid refinements, wei-domain bid selection (`BidCandidate`/`BidSource`), and Gloas block production that assembles local, gossip, and direct-builder candidates - network: process payload-bid and proposer-preference gossip, including the new `PayloadBidError` variants - client: construct the `Builders` service when the Gloas fork is scheduled and wire it into the beacon chain The HTTP API still serves `GET` produceBlockV4 at this point; the `POST` conversion and the `Eth-Builder-Url` round-trip land in the next PR. Change-Id: Ieccaee5db81bf871c19cef1b79fc48283be9dd51
…builder API 4/5) Fourth PR of the Gloas builder API stack (beacon-APIs sigp#630): - convert `/eth/v4/validator/blocks/{slot}` to POST with an optional `BuilderConfig` body (min_bid, builder_boost_factor, direct builders) - add `POST /eth/v1/validator/builder_preferences` for forwarding signed builder preferences - set `Eth-Builder-Url` on produceBlockV4 responses when a direct-builder bid wins, accept it on `POST /eth/v2/beacon/blocks`, and forward the signed block to that builder The validator client still uses the legacy GET methods at this point; it migrates in the final PR of this stack. Change-Id: I0ad30b8f36ad9b588ea1a0398220f92c9597bb95
…API 5/5) Final PR of the Gloas builder API stack: - sign builder request-auth and preferences (REQUEST_AUTH signing domain, web3signer message type) - add the builder configuration store (`builder_definitions.yml`) and book documentation - add the builder-preferences service and switch block production to `POST` produceBlockV4 with a `BuilderConfig` body, threading the `Eth-Builder-Url` header through block publication - remove the now-unused legacy `GET` produceBlockV4 client methods Change-Id: Iaeeaf6205a024e4fb9fd11aae6ac6a75978a8320
39cf3c2 to
9abe9a1
Compare
9abe9a1 to
58fba0d
Compare
…builder API 4/5) Fourth PR of the Gloas builder API stack (beacon-APIs sigp#630): - convert `/eth/v4/validator/blocks/{slot}` to POST with an optional `BuilderConfig` body (min_bid, builder_boost_factor, direct builders) - add `POST /eth/v1/validator/builder_preferences` for forwarding signed builder preferences - set `Eth-Builder-Url` on produceBlockV4 responses when a direct-builder bid wins, accept it on `POST /eth/v2/beacon/blocks`, and forward the signed block to that builder The validator client still uses the legacy GET methods at this point; it migrates in the final PR of this stack. Change-Id: I0ad30b8f36ad9b588ea1a0398220f92c9597bb95
…API 5/5) Final PR of the Gloas builder API stack: - sign builder request-auth and preferences (REQUEST_AUTH signing domain, web3signer message type) - add the builder configuration store (`builder_definitions.yml`) and book documentation - add the builder-preferences service and switch block production to `POST` produceBlockV4 with a `BuilderConfig` body, threading the `Eth-Builder-Url` header through block publication - remove the now-unused legacy `GET` produceBlockV4 client methods Change-Id: Iaeeaf6205a024e4fb9fd11aae6ac6a75978a8320
58fba0d to
2a6fc09
Compare
2a6fc09 to
a434c7d
Compare
|
This pull request has merge conflicts. Could you please resolve them @jimmygchen? 🙏 |
After publishing a Gloas beacon block selected from an external builder, the validator client immediately fetches the payload envelope from its beacon node. That endpoint only serves locally built envelopes, so it returns 404 before the selected builder publishes its envelope. The block still lands, but the validator client reports
Error whilst producing block.The validator client now fetches, signs, and publishes an envelope only when the selected bid has
builder_index == BUILDER_INDEX_SELF_BUILD. For an external builder, it stops after publishing the signed beacon block.